Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d443e630e3bd6b661a1a3ffb0f58daec2e1dfd37d3a9e56b62a76bc4ed158f0

Tx prefix hash: ae59d7ec8d38aca8d5d0af87a779349bb07d3d1578bbe77e0bd8cf6182ddd921
Tx public key: 3396881cea290b20e5f3ddeee8264ba9c27b09a8c64316c89ab94a4bc3b81250
Timestamp: 1736510004 Timestamp [UCT]: 2025-01-10 11:53:24 Age [y:d:h:m:s]: 00:304:02:11:06
Block: 1194296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214830 RingCT/type: yes/0
Extra: 013396881cea290b20e5f3ddeee8264ba9c27b09a8c64316c89ab94a4bc3b812500211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3543f25946379a86598bd517b5499d7b68780f20e5addc0e604b75d1c3fe3311 0.600000000000 1680865 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": 1194306, "vin": [ { "gen": { "height": 1194296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3543f25946379a86598bd517b5499d7b68780f20e5addc0e604b75d1c3fe3311" } } ], "extra": [ 1, 51, 150, 136, 28, 234, 41, 11, 32, 229, 243, 221, 238, 232, 38, 75, 169, 194, 123, 9, 168, 198, 67, 22, 200, 154, 185, 74, 75, 195, 184, 18, 80, 2, 17, 0, 0, 0, 4, 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