Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b73aecc3f8af8e79dfbc319df556f12ef8a3a75002a5309938474c11018307

Tx prefix hash: 1c5366a67704b915336843f8c88d9a3f55b3f3794fd738d69986838aaf085f29
Tx public key: 207604e6d0fbef187045ec46d8b4d74e0c3a5e02d0975b32e0282a26b29636a7
Timestamp: 1733680482 Timestamp [UCT]: 2024-12-08 17:54:42 Age [y:d:h:m:s]: 00:189:12:17:12
Block: 1170879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135174 RingCT/type: yes/0
Extra: 01207604e6d0fbef187045ec46d8b4d74e0c3a5e02d0975b32e0282a26b29636a70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f1742c2d248ec0c973edcb79532bd670f175b26ba584ee1a94ab1e17db09d10 0.600000000000 1656614 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": 1170889, "vin": [ { "gen": { "height": 1170879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f1742c2d248ec0c973edcb79532bd670f175b26ba584ee1a94ab1e17db09d10" } } ], "extra": [ 1, 32, 118, 4, 230, 208, 251, 239, 24, 112, 69, 236, 70, 216, 180, 215, 78, 12, 58, 94, 2, 208, 151, 91, 50, 224, 40, 42, 38, 178, 150, 54, 167, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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