Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a40a10565a262c51e865f172632d6afdba0caf17c6b16a8cf3dc92758d1d178e

Tx prefix hash: 08c525bf7426edd47c29e9a522eb501c49606ed9a32bf57a07b06deb14bf00ba
Tx public key: 21345e1e8e7e94dfaf4cc7fac3e80b275b12050dac41432921c40e719ab1c60d
Timestamp: 1731703349 Timestamp [UCT]: 2024-11-15 20:42:29 Age [y:d:h:m:s]: 00:154:09:46:07
Block: 1154486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110180 RingCT/type: yes/0
Extra: 0121345e1e8e7e94dfaf4cc7fac3e80b275b12050dac41432921c40e719ab1c60d021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 894fa726b1a5f1464c7ad36ffc172b87185955a94307933f7f09b3e8f0c589b8 0.600000000000 1640099 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": 1154496, "vin": [ { "gen": { "height": 1154486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "894fa726b1a5f1464c7ad36ffc172b87185955a94307933f7f09b3e8f0c589b8" } } ], "extra": [ 1, 33, 52, 94, 30, 142, 126, 148, 223, 175, 76, 199, 250, 195, 232, 11, 39, 91, 18, 5, 13, 172, 65, 67, 41, 33, 196, 14, 113, 154, 177, 198, 13, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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