Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ca77c80e0d0f58d40674a96acdeeb9ab320b5bb346e51af99b7428e9fd2f2b

Tx prefix hash: 7c4798435139ce443d7774d87e54775acb24e818849a23968f06a0d621958451
Tx public key: eaf5674bf1a318c151bc8d8cf82d96b63b2cdbb30412f4f3c782310f45c7aba0
Timestamp: 1711023038 Timestamp [UCT]: 2024-03-21 12:10:38 Age [y:d:h:m:s]: 01:089:02:32:03
Block: 983153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324569 RingCT/type: yes/0
Extra: 01eaf5674bf1a318c151bc8d8cf82d96b63b2cdbb30412f4f3c782310f45c7aba00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 666caf294b583b6f29ff2ac22fc4a8098f4c2742983528afcf2cdae74678f3b2 0.600000000000 1443276 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": 983163, "vin": [ { "gen": { "height": 983153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "666caf294b583b6f29ff2ac22fc4a8098f4c2742983528afcf2cdae74678f3b2" } } ], "extra": [ 1, 234, 245, 103, 75, 241, 163, 24, 193, 81, 188, 141, 140, 248, 45, 150, 182, 59, 44, 219, 179, 4, 18, 244, 243, 199, 130, 49, 15, 69, 199, 171, 160, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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