Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3fa04d400ad8b52ad2312a04339eb35e11e370df29e33f1e31b1fe7b8575a0

Tx prefix hash: 446bf0751e24a283a883c86ae8cc064b78dfcd1a0ef351b937756c15633139b5
Tx public key: 172ca71f6737aab112a70b3bfc95e9fc1b0a8d2ecd0fa7aa7b89810b1bf9c5b1
Timestamp: 1709176755 Timestamp [UCT]: 2024-02-29 03:19:15 Age [y:d:h:m:s]: 01:059:17:09:42
Block: 967831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303705 RingCT/type: yes/0
Extra: 01172ca71f6737aab112a70b3bfc95e9fc1b0a8d2ecd0fa7aa7b89810b1bf9c5b10211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4021e4498a3d15cf484f6815b020ef20214b36a79e90eb33dff80ac0cde462c8 0.600000000000 1427622 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": 967841, "vin": [ { "gen": { "height": 967831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4021e4498a3d15cf484f6815b020ef20214b36a79e90eb33dff80ac0cde462c8" } } ], "extra": [ 1, 23, 44, 167, 31, 103, 55, 170, 177, 18, 167, 11, 59, 252, 149, 233, 252, 27, 10, 141, 46, 205, 15, 167, 170, 123, 137, 129, 11, 27, 249, 197, 177, 2, 17, 0, 0, 0, 6, 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