Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e43d28d7813ad65772ffce633967dbd35bdb0d7e4d6505753bc7f5138539f07

Tx prefix hash: bdccdca1e951ba43b798f3d8a91d441df4c1829992d996130a85df2f0cd9fc43
Tx public key: 21aa751cd9ab48c7e59f76d36f39b40452b2d7f596a4ba1302b519d771296310
Timestamp: 1729216818 Timestamp [UCT]: 2024-10-18 02:00:18 Age [y:d:h:m:s]: 00:036:20:31:30
Block: 1133971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26296 RingCT/type: yes/0
Extra: 0121aa751cd9ab48c7e59f76d36f39b40452b2d7f596a4ba1302b519d771296310021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3544aea275e92944e3075046d8ff78b675be4ee9482e6ab4f782ebf90797298 0.600000000000 1617200 of 15

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": 1133981, "vin": [ { "gen": { "height": 1133971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3544aea275e92944e3075046d8ff78b675be4ee9482e6ab4f782ebf90797298" } } ], "extra": [ 1, 33, 170, 117, 28, 217, 171, 72, 199, 229, 159, 118, 211, 111, 57, 180, 4, 82, 178, 215, 245, 150, 164, 186, 19, 2, 181, 25, 215, 113, 41, 99, 16, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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