Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3522236befdd5ac7883d6b1852a83997ad6393a2cfce7be5b1fcd7a884c4afe3

Tx prefix hash: 0e639be0056a7a6a5893188088d9b5588e3f6f2b7d1924fc1c1dac6812784fdf
Tx public key: 11fa7f9f57cab26bd280e83a38944c9de8628336ef7f0c85d1b4710d2058d414
Timestamp: 1710530524 Timestamp [UCT]: 2024-03-15 19:22:04 Age [y:d:h:m:s]: 01:243:22:48:53
Block: 979063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433052 RingCT/type: yes/0
Extra: 0111fa7f9f57cab26bd280e83a38944c9de8628336ef7f0c85d1b4710d2058d41402110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4070326f2fb03dbdcb9023943d8eb610a36441925596b924567987f3559cfc88 0.600000000000 1439094 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": 979073, "vin": [ { "gen": { "height": 979063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4070326f2fb03dbdcb9023943d8eb610a36441925596b924567987f3559cfc88" } } ], "extra": [ 1, 17, 250, 127, 159, 87, 202, 178, 107, 210, 128, 232, 58, 56, 148, 76, 157, 232, 98, 131, 54, 239, 127, 12, 133, 209, 180, 113, 13, 32, 88, 212, 20, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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