Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e64851cfdd3cf18843d60b8fdf51a25fc89cfc88a15cee84a8336a703d4ed6

Tx prefix hash: 34948912dbb26d38c4f2e54412421d102a9cd87c40efd9fee7c5de6bf4f3895a
Tx public key: 164024a1409453b12e9b2e0e157a9540ad8a90011ef8053ba2b568f4266ee0a2
Timestamp: 1579010734 Timestamp [UCT]: 2020-01-14 14:05:34 Age [y:d:h:m:s]: 05:053:06:45:31
Block: 45320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1188316 RingCT/type: yes/0
Extra: 01164024a1409453b12e9b2e0e157a9540ad8a90011ef8053ba2b568f4266ee0a20211000000012264afe6000000000000000000

1 output(s) for total of 434.347040395000 dcy

stealth address amount amount idx
00: d08cd2cc57d5a8f9cfdacd64b1d1190226bdd34abd4e9d3439a11efc3ca6af24 434.347040395000 82771 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": 45330, "vin": [ { "gen": { "height": 45320 } } ], "vout": [ { "amount": 434347040395, "target": { "key": "d08cd2cc57d5a8f9cfdacd64b1d1190226bdd34abd4e9d3439a11efc3ca6af24" } } ], "extra": [ 1, 22, 64, 36, 161, 64, 148, 83, 177, 46, 155, 46, 14, 21, 122, 149, 64, 173, 138, 144, 1, 30, 248, 5, 59, 162, 181, 104, 244, 38, 110, 224, 162, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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