Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2bf1968b2ce9abf793b84fd60b1c713827176b0396827d93befe1b260bf214

Tx prefix hash: 26870b8b08413c5f820c6ece01ff253fb9cf9358b5bb8500520ceb9eef672c9e
Tx public key: 1591a03cb800f4a5be0c2dfc469b2714ed432b3728ecc1346416aa08ea80fe48
Timestamp: 1715839238 Timestamp [UCT]: 2024-05-16 06:00:38 Age [y:d:h:m:s]: 01:172:09:04:28
Block: 1023063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381797 RingCT/type: yes/0
Extra: 011591a03cb800f4a5be0c2dfc469b2714ed432b3728ecc1346416aa08ea80fe4802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec30f7cd8bbd0f14af5d8a2818bf05a1caf5f9a2a8f20bcdeb505c7ca86e7963 0.600000000000 1487846 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": 1023073, "vin": [ { "gen": { "height": 1023063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec30f7cd8bbd0f14af5d8a2818bf05a1caf5f9a2a8f20bcdeb505c7ca86e7963" } } ], "extra": [ 1, 21, 145, 160, 60, 184, 0, 244, 165, 190, 12, 45, 252, 70, 155, 39, 20, 237, 67, 43, 55, 40, 236, 193, 52, 100, 22, 170, 8, 234, 128, 254, 72, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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