Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6df0a0f77cc7088308f9eee7a63eb5e279f524bf2f265c31164baf3e00341a70

Tx prefix hash: 4201a01799cdafa30149b14d122209ab9756ecc0385749dab8247d145e775332
Tx public key: 1c8ae1571a015db7f92a483089b0bfe917d9cdaca245fda245b482fd9461b147
Timestamp: 1710119194 Timestamp [UCT]: 2024-03-11 01:06:34 Age [y:d:h:m:s]: 01:098:15:31:41
Block: 975647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331424 RingCT/type: yes/0
Extra: 011c8ae1571a015db7f92a483089b0bfe917d9cdaca245fda245b482fd9461b1470211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62739bac7581bc966d3fd855a9a54c5f5ed18255713f12b4bf2a0ad1cd9870b4 0.600000000000 1435620 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": 975657, "vin": [ { "gen": { "height": 975647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62739bac7581bc966d3fd855a9a54c5f5ed18255713f12b4bf2a0ad1cd9870b4" } } ], "extra": [ 1, 28, 138, 225, 87, 26, 1, 93, 183, 249, 42, 72, 48, 137, 176, 191, 233, 23, 217, 205, 172, 162, 69, 253, 162, 69, 180, 130, 253, 148, 97, 177, 71, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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