Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e18f8f9bc27c73c72be7cdbb3e728b7208323cbe6ba889a3dfab98cf1be1fe30

Tx prefix hash: 59a65c4587af513854b9c9c91ec6ca435d89067ec0e54c3da1d1f3982fd6222a
Tx public key: dcff14f1eb2f924c6c807ebc3ae233a4c2c458d9a10eda43dca13a8876245455
Timestamp: 1705766637 Timestamp [UCT]: 2024-01-20 16:03:57 Age [y:d:h:m:s]: 01:290:11:07:15
Block: 939526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466401 RingCT/type: yes/0
Extra: 01dcff14f1eb2f924c6c807ebc3ae233a4c2c458d9a10eda43dca13a88762454550211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f85ab15eda42a4855c2e983c189a6638156edf5c4a69835c777632b7ef1cf9db 0.600000000000 1397634 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": 939536, "vin": [ { "gen": { "height": 939526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f85ab15eda42a4855c2e983c189a6638156edf5c4a69835c777632b7ef1cf9db" } } ], "extra": [ 1, 220, 255, 20, 241, 235, 47, 146, 76, 108, 128, 126, 188, 58, 226, 51, 164, 194, 196, 88, 217, 161, 14, 218, 67, 220, 161, 58, 136, 118, 36, 84, 85, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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