Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6d18fd6ca83a32821746ce16d078958edb4183d34be798705bdd92e81bf5e8a

Tx prefix hash: 547a85dc84a290abcde0a9395d438b3e1a1dc5a8cd0bdee94a7a984aa963f84a
Tx public key: 721c0be84827ceadf83fd9e8a794ca0fad5dad0a5681a4775a4ad0d8126923bb
Timestamp: 1634229204 Timestamp [UCT]: 2021-10-14 16:33:24 Age [y:d:h:m:s]: 04:021:15:35:43
Block: 352980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1051682 RingCT/type: yes/0
Extra: 01721c0be84827ceadf83fd9e8a794ca0fad5dad0a5681a4775a4ad0d8126923bb021100000005f60c5d7e000000000000000000

1 output(s) for total of 41.536619703000 dcy

stealth address amount amount idx
00: 25c0f1fb8089ccb642579a19c8b3b3c997c7508be8b5e49a038c6fd43c408253 41.536619703000 721370 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": 352990, "vin": [ { "gen": { "height": 352980 } } ], "vout": [ { "amount": 41536619703, "target": { "key": "25c0f1fb8089ccb642579a19c8b3b3c997c7508be8b5e49a038c6fd43c408253" } } ], "extra": [ 1, 114, 28, 11, 232, 72, 39, 206, 173, 248, 63, 217, 232, 167, 148, 202, 15, 173, 93, 173, 10, 86, 129, 164, 119, 90, 74, 208, 216, 18, 105, 35, 187, 2, 17, 0, 0, 0, 5, 246, 12, 93, 126, 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