Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0bf1191bab01325f41672f1ee7ae1c97897b14d0df26f5413def8567018384

Tx prefix hash: 5579692378b7a6f46be8a99e64fac11e077bc0551986585c360094d0eda8bad0
Tx public key: 0895d9e8b28b6fc84cb1f7628a5fc4c4161df847206c43d348c91b5faca049b3
Timestamp: 1732807064 Timestamp [UCT]: 2024-11-28 15:17:44 Age [y:d:h:m:s]: 01:022:18:27:09
Block: 1163641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274712 RingCT/type: yes/0
Extra: 010895d9e8b28b6fc84cb1f7628a5fc4c4161df847206c43d348c91b5faca049b30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef744c7e929c578943fb14905b78440dceefdfc345f1fb003afe87975c05955d 0.600000000000 1649308 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": 1163651, "vin": [ { "gen": { "height": 1163641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef744c7e929c578943fb14905b78440dceefdfc345f1fb003afe87975c05955d" } } ], "extra": [ 1, 8, 149, 217, 232, 178, 139, 111, 200, 76, 177, 247, 98, 138, 95, 196, 196, 22, 29, 248, 71, 32, 108, 67, 211, 72, 201, 27, 95, 172, 160, 73, 179, 2, 17, 0, 0, 0, 1, 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