Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25878fe6304a8724160a776dfcdedfb93a230617a5c7b31a5652b8e64c9beedb

Tx prefix hash: 6f9af6e0e5184bc5d5f14626037267a8707c79ad9267b61f9726f321a69c61e3
Tx public key: e1e6e5d8f7e0a10b950b1c919c5d9b04e245832585a9b868a0d25c31bfd93c39
Timestamp: 1710538250 Timestamp [UCT]: 2024-03-15 21:30:50 Age [y:d:h:m:s]: 01:013:10:59:47
Block: 979136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270577 RingCT/type: yes/0
Extra: 01e1e6e5d8f7e0a10b950b1c919c5d9b04e245832585a9b868a0d25c31bfd93c39021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b7b373a6eb709bd44af5e39d0066edfde23da6d0c24687ae0d82dcf3e7731b2 0.600000000000 1439169 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": 979146, "vin": [ { "gen": { "height": 979136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b7b373a6eb709bd44af5e39d0066edfde23da6d0c24687ae0d82dcf3e7731b2" } } ], "extra": [ 1, 225, 230, 229, 216, 247, 224, 161, 11, 149, 11, 28, 145, 156, 93, 155, 4, 226, 69, 131, 37, 133, 169, 184, 104, 160, 210, 92, 49, 191, 217, 60, 57, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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