Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854cc448f52609620ed3cb558538eb6862dd0633be5257c6ef3407bb2b299358

Tx prefix hash: fa44ada1303f4457a943624a0b5d4a30de3820cc5fbd2a5471cf19d136ce0328
Tx public key: 3fcfb2ea9a9990c1e87826f8003a93e21d6cd5ae33366d01ce35245da3be073a
Timestamp: 1576255926 Timestamp [UCT]: 2019-12-13 16:52:06 Age [y:d:h:m:s]: 05:346:16:23:37
Block: 26389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1391902 RingCT/type: yes/0
Extra: 013fcfb2ea9a9990c1e87826f8003a93e21d6cd5ae33366d01ce35245da3be073a0211000000044ac5aa02000000000000000000

1 output(s) for total of 501.837551961000 dcy

stealth address amount amount idx
00: 790b19fa73a1d43acf5349d7a071daf20034d9048bf1eb6c19a7e55db185c4f7 501.837551961000 43676 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": 26399, "vin": [ { "gen": { "height": 26389 } } ], "vout": [ { "amount": 501837551961, "target": { "key": "790b19fa73a1d43acf5349d7a071daf20034d9048bf1eb6c19a7e55db185c4f7" } } ], "extra": [ 1, 63, 207, 178, 234, 154, 153, 144, 193, 232, 120, 38, 248, 0, 58, 147, 226, 29, 108, 213, 174, 51, 54, 109, 1, 206, 53, 36, 93, 163, 190, 7, 58, 2, 17, 0, 0, 0, 4, 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