Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c7116847d51c27e63379cec51e3ceed8ec5fe2b855be4bc129a23b0014f7cc2

Tx prefix hash: 7bf028e9132349e5ca700732e273b1801bb7d2adf9f39a98577954f6c587e8d6
Tx public key: 31bd93c4763b9695f6b1f821086d8eab2f38527e315d81ffaf470c46cabd6313
Timestamp: 1736989058 Timestamp [UCT]: 2025-01-16 00:57:38 Age [y:d:h:m:s]: 00:153:23:19:43
Block: 1198251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109746 RingCT/type: yes/0
Extra: 0131bd93c4763b9695f6b1f821086d8eab2f38527e315d81ffaf470c46cabd6313021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e12d161622f4a9d96e3d6c9a356515d10cd8176f6f7ab0cef2b1316dcdaeaced 0.600000000000 1684872 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": 1198261, "vin": [ { "gen": { "height": 1198251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e12d161622f4a9d96e3d6c9a356515d10cd8176f6f7ab0cef2b1316dcdaeaced" } } ], "extra": [ 1, 49, 189, 147, 196, 118, 59, 150, 149, 246, 177, 248, 33, 8, 109, 142, 171, 47, 56, 82, 126, 49, 93, 129, 255, 175, 71, 12, 70, 202, 189, 99, 19, 2, 17, 0, 0, 0, 8, 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