Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cbf65683bf5d0bfec00b4d3c0c5684632ed4d4a83cb1a6ddca4f056e38e50d3

Tx prefix hash: a9925d0b8f104fcbdc6f0b9ee1201e8fc2b8d9f9feeb642dbb4420ac238b4b0f
Tx public key: e5ad21832487fd3ce02e62853bfd42b186628f17cbe227169a01948b75825de0
Timestamp: 1582110303 Timestamp [UCT]: 2020-02-19 11:05:03 Age [y:d:h:m:s]: 05:260:02:46:27
Block: 68092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336734 RingCT/type: yes/0
Extra: 01e5ad21832487fd3ce02e62853bfd42b186628f17cbe227169a01948b75825de00211000000014ac5aa02000000000000000000

1 output(s) for total of 365.117917238000 dcy

stealth address amount amount idx
00: bd3ed8fa820a893f1130e8edb974f5b1ca4356045a7eae1b7e8a6e567270d302 365.117917238000 125458 of 0

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": 68102, "vin": [ { "gen": { "height": 68092 } } ], "vout": [ { "amount": 365117917238, "target": { "key": "bd3ed8fa820a893f1130e8edb974f5b1ca4356045a7eae1b7e8a6e567270d302" } } ], "extra": [ 1, 229, 173, 33, 131, 36, 135, 253, 60, 224, 46, 98, 133, 59, 253, 66, 177, 134, 98, 143, 23, 203, 226, 39, 22, 154, 1, 148, 139, 117, 130, 93, 224, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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