Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d59aed1b03b9f49c4bea1da54136629cd0de551d77d71b4e83db4a5f79105665

Tx prefix hash: 2e394cc481283fbbff463a447d7f05c1e5674e05876b54307a439452d81205ee
Tx public key: e93457b1ff57d8b445a6baeb8b0a1f825181eaca1ea62cfaba5b2840d11d218a
Timestamp: 1738048818 Timestamp [UCT]: 2025-01-28 07:20:18 Age [y:d:h:m:s]: 00:345:01:47:29
Block: 1206783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244453 RingCT/type: yes/0
Extra: 01e93457b1ff57d8b445a6baeb8b0a1f825181eaca1ea62cfaba5b2840d11d218a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52064f41b7f7519bd2f8b47db5ad443d5739e2b29c337e260aad03e86defe00d 0.600000000000 1693496 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": 1206793, "vin": [ { "gen": { "height": 1206783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52064f41b7f7519bd2f8b47db5ad443d5739e2b29c337e260aad03e86defe00d" } } ], "extra": [ 1, 233, 52, 87, 177, 255, 87, 216, 180, 69, 166, 186, 235, 139, 10, 31, 130, 81, 129, 234, 202, 30, 166, 44, 250, 186, 91, 40, 64, 209, 29, 33, 138, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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