Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b386d26eadd352659645fb6635ac1e3fb75f6d9bffbbefd88874ac076e1c7ed1

Tx prefix hash: 864e3f058fb68c86ba155bc93491747a9f64f847e8e3543dde6905857e9b61bc
Tx public key: 33f64d3a71024e67fd5a9ec1b2c5c0ab669c8eb3e654bc71a76c2ef25ebb0d1d
Timestamp: 1721616002 Timestamp [UCT]: 2024-07-22 02:40:02 Age [y:d:h:m:s]: 00:167:03:09:48
Block: 1070945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119595 RingCT/type: yes/0
Extra: 0133f64d3a71024e67fd5a9ec1b2c5c0ab669c8eb3e654bc71a76c2ef25ebb0d1d02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e6644b5d4aeef7b07770af1af9ca360705c73bda8e6cff503f5852ff8912a62 0.600000000000 1542984 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": 1070955, "vin": [ { "gen": { "height": 1070945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e6644b5d4aeef7b07770af1af9ca360705c73bda8e6cff503f5852ff8912a62" } } ], "extra": [ 1, 51, 246, 77, 58, 113, 2, 78, 103, 253, 90, 158, 193, 178, 197, 192, 171, 102, 156, 142, 179, 230, 84, 188, 113, 167, 108, 46, 242, 94, 187, 13, 29, 2, 17, 0, 0, 0, 10, 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