Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f10609672f57a3698028e944b6f201fe52424d7a42c0b943fbd2eab939616da

Tx prefix hash: eda2d5819a55952fc1402ed5bd2dd3124310beb7ff753e5e5ed22ee47aa0fd5a
Tx public key: 901df1ae2e7337c4094dcd22caf71449c9c39d7bb4ec846f8b6d68b8745452b0
Timestamp: 1716241599 Timestamp [UCT]: 2024-05-20 21:46:39 Age [y:d:h:m:s]: 00:236:12:05:19
Block: 1026403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169258 RingCT/type: yes/0
Extra: 01901df1ae2e7337c4094dcd22caf71449c9c39d7bb4ec846f8b6d68b8745452b002110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39ee78d2451512773fcdae24cae0f10ba071a52983343a069545d97e7334ac8d 0.600000000000 1493468 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": 1026413, "vin": [ { "gen": { "height": 1026403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39ee78d2451512773fcdae24cae0f10ba071a52983343a069545d97e7334ac8d" } } ], "extra": [ 1, 144, 29, 241, 174, 46, 115, 55, 196, 9, 77, 205, 34, 202, 247, 20, 73, 201, 195, 157, 123, 180, 236, 132, 111, 139, 109, 104, 184, 116, 84, 82, 176, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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