Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48ab0a63e75f7fe591386f98accecfd60e80ab42e648cc277a75d1a4e6c2b078

Tx prefix hash: db72a3a6c25bca0d3c6af925907dde12907a0e8bc66de95d794821c0d1eccf88
Tx public key: a92060c38d4a0cad7bbafdf02631a7f9615934dde9bba933a2034cb43bc1b5d3
Timestamp: 1738190295 Timestamp [UCT]: 2025-01-29 22:38:15 Age [y:d:h:m:s]: 00:320:22:54:11
Block: 1207943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227176 RingCT/type: yes/0
Extra: 01a92060c38d4a0cad7bbafdf02631a7f9615934dde9bba933a2034cb43bc1b5d3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b18b9fbc0f34abb539315e52a0406df9ef22cf2d49b1e1e13cf571ed4696eebb 0.600000000000 1694670 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": 1207953, "vin": [ { "gen": { "height": 1207943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b18b9fbc0f34abb539315e52a0406df9ef22cf2d49b1e1e13cf571ed4696eebb" } } ], "extra": [ 1, 169, 32, 96, 195, 141, 74, 12, 173, 123, 186, 253, 240, 38, 49, 167, 249, 97, 89, 52, 221, 233, 187, 169, 51, 162, 3, 76, 180, 59, 193, 181, 211, 2, 17, 0, 0, 0, 2, 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