Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54705aefbcc4a37a637be2899f91a9cf025a8ec01be0b93f21c38ca3f559fa40

Tx prefix hash: bc0ce7433c1ef7697502da84005d547976d8e71ee5ef2d5ebaacf728b44f5d6a
Tx public key: 8dea239bc6e903e7bce5b13365c1da606706bd986c4e19414316fccda2487d60
Timestamp: 1629419674 Timestamp [UCT]: 2021-08-20 00:34:34 Age [y:d:h:m:s]: 04:073:19:40:26
Block: 317356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084810 RingCT/type: yes/0
Extra: 018dea239bc6e903e7bce5b13365c1da606706bd986c4e19414316fccda2487d60021100000020282c04e2000000000000000000

1 output(s) for total of 54.509010243000 dcy

stealth address amount amount idx
00: eb0631017db648e763d7f1593808d8371f9c857de0a9fba95340a37b32ebc5a8 54.509010243000 659935 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": 317366, "vin": [ { "gen": { "height": 317356 } } ], "vout": [ { "amount": 54509010243, "target": { "key": "eb0631017db648e763d7f1593808d8371f9c857de0a9fba95340a37b32ebc5a8" } } ], "extra": [ 1, 141, 234, 35, 155, 198, 233, 3, 231, 188, 229, 177, 51, 101, 193, 218, 96, 103, 6, 189, 152, 108, 78, 25, 65, 67, 22, 252, 205, 162, 72, 125, 96, 2, 17, 0, 0, 0, 32, 40, 44, 4, 226, 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