Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d958e34adacb0f4fff9502698b3104f741b9be835c294834faaab3021c737f5

Tx prefix hash: a1dc97236f6527825f8e9351cfe31e4d1a500a5d2f92c58b52cca85197037df0
Tx public key: 3c16fcb4c6fea53bb7f812408e80f00c44510f5816752489788cae9c61ed4f43
Timestamp: 1721263710 Timestamp [UCT]: 2024-07-18 00:48:30 Age [y:d:h:m:s]: 00:129:06:10:47
Block: 1068050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92468 RingCT/type: yes/0
Extra: 013c16fcb4c6fea53bb7f812408e80f00c44510f5816752489788cae9c61ed4f4302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac4d44d7854b9e95db554b2fb7aa6f6ea1ca77b6622ed2f560790e97221656b8 0.600000000000 1539043 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": 1068060, "vin": [ { "gen": { "height": 1068050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac4d44d7854b9e95db554b2fb7aa6f6ea1ca77b6622ed2f560790e97221656b8" } } ], "extra": [ 1, 60, 22, 252, 180, 198, 254, 165, 59, 183, 248, 18, 64, 142, 128, 240, 12, 68, 81, 15, 88, 22, 117, 36, 137, 120, 140, 174, 156, 97, 237, 79, 67, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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