Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52b19ffcd85e5cc8c7f4390958e2848332840ef8ce572247c4428a70416e9ce

Tx prefix hash: 53cddfef077456a9eca70c4bd3bbed18942e834df2abd472ef0cf442235c5e41
Tx public key: 775baf72221f9e5fffde3bf0b88a9f6b6a46524c2302bb4d878510ecfb48b7f9
Timestamp: 1711600900 Timestamp [UCT]: 2024-03-28 04:41:40 Age [y:d:h:m:s]: 00:362:05:25:07
Block: 987939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258959 RingCT/type: yes/0
Extra: 01775baf72221f9e5fffde3bf0b88a9f6b6a46524c2302bb4d878510ecfb48b7f90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 864014f9e057e0f7e53d66a1dd66f04946d9e60e549cfcd750997f1b0d7d9bd6 0.600000000000 1448200 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": 987949, "vin": [ { "gen": { "height": 987939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "864014f9e057e0f7e53d66a1dd66f04946d9e60e549cfcd750997f1b0d7d9bd6" } } ], "extra": [ 1, 119, 91, 175, 114, 34, 31, 158, 95, 255, 222, 59, 240, 184, 138, 159, 107, 106, 70, 82, 76, 35, 2, 187, 77, 135, 133, 16, 236, 251, 72, 183, 249, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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