Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb4df3b471a456f256c011c109cdb67b2f9adec219827d7b620af16ef4611f1a

Tx prefix hash: d8831cdd7d7f42352344fa6855e0fde32804bfdbae96e4dbed1cabf889fe9884
Tx public key: d01ea61766f75c2d75f86733fd534032718fc25da58d6fa318d0a5f040d17d21
Timestamp: 1735565686 Timestamp [UCT]: 2024-12-30 13:34:46 Age [y:d:h:m:s]: 00:170:14:50:04
Block: 1186475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121626 RingCT/type: yes/0
Extra: 01d01ea61766f75c2d75f86733fd534032718fc25da58d6fa318d0a5f040d17d210211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3372d3a3eef44f5b165c905fd3f988853995e0ed7d92eb42fcd3ae9a6939b96 0.600000000000 1672956 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": 1186485, "vin": [ { "gen": { "height": 1186475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3372d3a3eef44f5b165c905fd3f988853995e0ed7d92eb42fcd3ae9a6939b96" } } ], "extra": [ 1, 208, 30, 166, 23, 102, 247, 92, 45, 117, 248, 103, 51, 253, 83, 64, 50, 113, 143, 194, 93, 165, 141, 111, 163, 24, 208, 165, 240, 64, 209, 125, 33, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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