Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5217eb714a03ed768fc391f0eeaf3ce7e17b223ea7b908ac0d877e321037c397

Tx prefix hash: 0c5cc87c2cf2b909f8cdfc03d65933edf1e69fe9be61947f1479a579192667b2
Tx public key: 8e888a5f3f896d950776e3f308416578577f7f3cf462c67e8e2f40d5b3928219
Timestamp: 1729759777 Timestamp [UCT]: 2024-10-24 08:49:37 Age [y:d:h:m:s]: 00:014:03:46:53
Block: 1138434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10090 RingCT/type: yes/0
Extra: 018e888a5f3f896d950776e3f308416578577f7f3cf462c67e8e2f40d5b39282190211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e95c0949b8b9be55618a7bedaab5b5cba65caa604822e853e41d1fd51b0b25f 0.600000000000 1622107 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": 1138444, "vin": [ { "gen": { "height": 1138434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e95c0949b8b9be55618a7bedaab5b5cba65caa604822e853e41d1fd51b0b25f" } } ], "extra": [ 1, 142, 136, 138, 95, 63, 137, 109, 149, 7, 118, 227, 243, 8, 65, 101, 120, 87, 127, 127, 60, 244, 98, 198, 126, 142, 47, 64, 213, 179, 146, 130, 25, 2, 17, 0, 0, 0, 2, 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