Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af7534c04bdbb159017d8f94fa38b9eef62f8b9c51ae95e2879d11b0d368ee91

Tx prefix hash: a3d93800bc73be95eeb3d79d8a3621206af9998ec215373621a57bd0a83fdf1d
Tx public key: 7fc4eeb2b654f487b1f4c734181884cbea137f8b2033a2ef2e55e7709fb0eb5a
Timestamp: 1732306460 Timestamp [UCT]: 2024-11-22 20:14:20 Age [y:d:h:m:s]: 00:205:13:21:35
Block: 1159488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146657 RingCT/type: yes/0
Extra: 017fc4eeb2b654f487b1f4c734181884cbea137f8b2033a2ef2e55e7709fb0eb5a02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21277a0f28069753d8fb4f289162cfc8d89bbf16bd7763382fcef873f8304429 0.600000000000 1645125 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": 1159498, "vin": [ { "gen": { "height": 1159488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21277a0f28069753d8fb4f289162cfc8d89bbf16bd7763382fcef873f8304429" } } ], "extra": [ 1, 127, 196, 238, 178, 182, 84, 244, 135, 177, 244, 199, 52, 24, 24, 132, 203, 234, 19, 127, 139, 32, 51, 162, 239, 46, 85, 231, 112, 159, 176, 235, 90, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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