Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d48f0d5ef6699606477d08c3d090a70f1be11762143f3802df9bf91d4bdb37f

Tx prefix hash: 6559ca2e3a537ef67bd2c81575a18a052739825c17517784b827d341c649c277
Tx public key: 4479cc615eca5c4f116294e8c47cc6afc8474b6d0a8ecbb5a3275bdf5306875a
Timestamp: 1704493397 Timestamp [UCT]: 2024-01-05 22:23:17 Age [y:d:h:m:s]: 01:094:13:22:44
Block: 928985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328699 RingCT/type: yes/0
Extra: 014479cc615eca5c4f116294e8c47cc6afc8474b6d0a8ecbb5a3275bdf5306875a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 632c962cdcd7cb5c5d1c7746dfb5260f2729bebb89d1fe1204d6f3b8258e7145 0.600000000000 1386851 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": 928995, "vin": [ { "gen": { "height": 928985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "632c962cdcd7cb5c5d1c7746dfb5260f2729bebb89d1fe1204d6f3b8258e7145" } } ], "extra": [ 1, 68, 121, 204, 97, 94, 202, 92, 79, 17, 98, 148, 232, 196, 124, 198, 175, 200, 71, 75, 109, 10, 142, 203, 181, 163, 39, 91, 223, 83, 6, 135, 90, 2, 17, 0, 0, 0, 2, 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