Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01466c6208192b564d4da5c1cca57814002bb6c47cd60c3a36c708b0fac5086a

Tx prefix hash: 6f1409b93f0fff7b2bc0044fbc4d5b04c90647d28b31b073f964980b7fb922d6
Tx public key: d66a8f56158f8df70cc3543d2a41477f5f76ca2b35b5df83293d759617254288
Timestamp: 1705097656 Timestamp [UCT]: 2024-01-12 22:14:16 Age [y:d:h:m:s]: 01:300:03:09:26
Block: 933990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473336 RingCT/type: yes/0
Extra: 01d66a8f56158f8df70cc3543d2a41477f5f76ca2b35b5df83293d75961725428802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ef5951504d5f4440c11c9c36bb3b3cf2b262db7260cbdec4bf351610faadb9b 0.600000000000 1391974 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": 934000, "vin": [ { "gen": { "height": 933990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ef5951504d5f4440c11c9c36bb3b3cf2b262db7260cbdec4bf351610faadb9b" } } ], "extra": [ 1, 214, 106, 143, 86, 21, 143, 141, 247, 12, 195, 84, 61, 42, 65, 71, 127, 95, 118, 202, 43, 53, 181, 223, 131, 41, 61, 117, 150, 23, 37, 66, 136, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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