Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c92d6a02222b88b6f193f3bd185772ec9ee4605f33dc471241611c86d727ff1d

Tx prefix hash: 4bec7283f4e54907a9bc1ea945778d1d46e672a4d29ce35d48293475f4307cbf
Tx public key: 3eae408753f8a614e58a00a80bc6a30ef4eabeeb50416c88f79cc41ef7bc202c
Timestamp: 1726214728 Timestamp [UCT]: 2024-09-13 08:05:28 Age [y:d:h:m:s]: 00:162:19:57:57
Block: 1109075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116171 RingCT/type: yes/0
Extra: 013eae408753f8a614e58a00a80bc6a30ef4eabeeb50416c88f79cc41ef7bc202c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04bd11c6b3cdb3e8f39483439b416d230943dbc330241e6617f4dc4c4bd634f 0.600000000000 1587196 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": 1109085, "vin": [ { "gen": { "height": 1109075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04bd11c6b3cdb3e8f39483439b416d230943dbc330241e6617f4dc4c4bd634f" } } ], "extra": [ 1, 62, 174, 64, 135, 83, 248, 166, 20, 229, 138, 0, 168, 11, 198, 163, 14, 244, 234, 190, 235, 80, 65, 108, 136, 247, 156, 196, 30, 247, 188, 32, 44, 2, 17, 0, 0, 0, 5, 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