Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4f824e9da50319fedec929caf80815ae1cc04ded0fd2deb3f9425d275f47a98

Tx prefix hash: e41929cb1d52c0d3fb5d7cce4f4a1e3dfa812999ab00fde300883e916e01d904
Tx public key: 58e826e721baa7504c4df511ab9a8e1c501de1f8827a9b7b0221e86b30425a46
Timestamp: 1738151930 Timestamp [UCT]: 2025-01-29 11:58:50 Age [y:d:h:m:s]: 00:294:20:02:39
Block: 1207623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208482 RingCT/type: yes/0
Extra: 0158e826e721baa7504c4df511ab9a8e1c501de1f8827a9b7b0221e86b30425a460211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bed41c97873fbbedd5b335a40b3df51b7849a438001dbd33e2556423a9f756d 0.600000000000 1694348 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": 1207633, "vin": [ { "gen": { "height": 1207623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bed41c97873fbbedd5b335a40b3df51b7849a438001dbd33e2556423a9f756d" } } ], "extra": [ 1, 88, 232, 38, 231, 33, 186, 167, 80, 76, 77, 245, 17, 171, 154, 142, 28, 80, 29, 225, 248, 130, 122, 155, 123, 2, 33, 232, 107, 48, 66, 90, 70, 2, 17, 0, 0, 0, 1, 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