Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3698278ec0070ceb6b32b8986ecee45ea206a08d125309082d28f34c9494c86

Tx prefix hash: 90cf678394c2fa26dada4ff033eb5d243e92f0a9f85f9f01265323507ae7281f
Tx public key: 33fd60df5ee52e45cae4a0a059d0d15aed97c4c6fe8ed776ab08c05550e314cb
Timestamp: 1737890707 Timestamp [UCT]: 2025-01-26 11:25:07 Age [y:d:h:m:s]: 00:331:08:22:40
Block: 1205681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234393 RingCT/type: yes/0
Extra: 0133fd60df5ee52e45cae4a0a059d0d15aed97c4c6fe8ed776ab08c05550e314cb021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43539c3070e52064fa1a9dc3d64bac1875d8c9dc287d1490575d03cd27bcb9f6 0.600000000000 1692380 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": 1205691, "vin": [ { "gen": { "height": 1205681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43539c3070e52064fa1a9dc3d64bac1875d8c9dc287d1490575d03cd27bcb9f6" } } ], "extra": [ 1, 51, 253, 96, 223, 94, 229, 46, 69, 202, 228, 160, 160, 89, 208, 209, 90, 237, 151, 196, 198, 254, 142, 215, 118, 171, 8, 192, 85, 80, 227, 20, 203, 2, 17, 0, 0, 0, 7, 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