Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bba0466ef5de1f4d83dc67e44f8a25e116b119f5269a09090560e477c52d005

Tx prefix hash: 01662f3ddbcc7ca7308961ca13c60fb9c55cf379ceed0c54df1dd5ced26507f1
Tx public key: 3a4a4e185091e5849ecf15ef06c3a428d6ee3f99a7562ddbbc839ea1ff2d0cf8
Timestamp: 1722405085 Timestamp [UCT]: 2024-07-31 05:51:25 Age [y:d:h:m:s]: 00:179:04:02:04
Block: 1077496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128138 RingCT/type: yes/0
Extra: 013a4a4e185091e5849ecf15ef06c3a428d6ee3f99a7562ddbbc839ea1ff2d0cf802110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0f792699a8b271b97a38e41e2d02804be14dd5c5056087e00c740bc6bde8409 0.600000000000 1550045 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": 1077506, "vin": [ { "gen": { "height": 1077496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0f792699a8b271b97a38e41e2d02804be14dd5c5056087e00c740bc6bde8409" } } ], "extra": [ 1, 58, 74, 78, 24, 80, 145, 229, 132, 158, 207, 21, 239, 6, 195, 164, 40, 214, 238, 63, 153, 167, 86, 45, 219, 188, 131, 158, 161, 255, 45, 12, 248, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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