Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f96c61427cdc12918bd9cd75e7da102a0a934f14165102c68d8f01a0eaa6ae47

Tx prefix hash: 94c39caa4a098f2b0f2e3e010549d3473aa8dfa79799359203fae3724402aa7d
Tx public key: 1cf1a196cbf33c9491cf5cf0aab39fe69e42c3d8fce395c01c2c35a98a8bc690
Timestamp: 1720753416 Timestamp [UCT]: 2024-07-12 03:03:36 Age [y:d:h:m:s]: 01:119:10:48:43
Block: 1063813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343876 RingCT/type: yes/0
Extra: 011cf1a196cbf33c9491cf5cf0aab39fe69e42c3d8fce395c01c2c35a98a8bc69002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc24fa14b16f7f7452c732ae76122c404c1e97690137d9e98951bbd7c15e5afe 0.600000000000 1534330 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1063823, "vin": [ { "gen": { "height": 1063813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc24fa14b16f7f7452c732ae76122c404c1e97690137d9e98951bbd7c15e5afe" } } ], "extra": [ 1, 28, 241, 161, 150, 203, 243, 60, 148, 145, 207, 92, 240, 170, 179, 159, 230, 158, 66, 195, 216, 252, 227, 149, 192, 28, 44, 53, 169, 138, 139, 198, 144, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8