Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88dd9a0c5a0b3214751e6013206d9cbefc5ae1fd03ca6997c24916de11627704

Tx prefix hash: f79e8cdf41db7f55e431ca0b3b23f5a38a4d53560129f776263852a23b94560f
Tx public key: 9d21dacb1479d183a51ec602e1e314c54e98acbd5ccf652753238fdf99f2eb2c
Timestamp: 1730672491 Timestamp [UCT]: 2024-11-03 22:21:31 Age [y:d:h:m:s]: 00:020:09:04:37
Block: 1145951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14586 RingCT/type: yes/0
Extra: 019d21dacb1479d183a51ec602e1e314c54e98acbd5ccf652753238fdf99f2eb2c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52101f13fe87bdc67ff8cd784fa7e18d332b1741e56c8e0a53a99ac46435b898 0.600000000000 1630484 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": 1145961, "vin": [ { "gen": { "height": 1145951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52101f13fe87bdc67ff8cd784fa7e18d332b1741e56c8e0a53a99ac46435b898" } } ], "extra": [ 1, 157, 33, 218, 203, 20, 121, 209, 131, 165, 30, 198, 2, 225, 227, 20, 197, 78, 152, 172, 189, 92, 207, 101, 39, 83, 35, 143, 223, 153, 242, 235, 44, 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