Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afead87e51949c966ed35e4eab82bc5378c00a026acc47c6b92fc2dd5410c7e2

Tx prefix hash: cd68256b94cab311d1ba5c9687df59ccd4f4cdd373f055bcd60a3468c78ace5f
Tx public key: 4a2b3ee27604224c1c74f5b685d654f02fb4e85a0b6fd34a9ab88bcbf509ea6e
Timestamp: 1713097944 Timestamp [UCT]: 2024-04-14 12:32:24 Age [y:d:h:m:s]: 00:317:08:56:04
Block: 1000316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226893 RingCT/type: yes/0
Extra: 014a2b3ee27604224c1c74f5b685d654f02fb4e85a0b6fd34a9ab88bcbf509ea6e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e30d5dc84848ac08954d557e4736450e7b9f4eb31000c63e85fadaee40d8ac82 0.600000000000 1460814 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": 1000326, "vin": [ { "gen": { "height": 1000316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e30d5dc84848ac08954d557e4736450e7b9f4eb31000c63e85fadaee40d8ac82" } } ], "extra": [ 1, 74, 43, 62, 226, 118, 4, 34, 76, 28, 116, 245, 182, 133, 214, 84, 240, 47, 180, 232, 90, 11, 111, 211, 74, 154, 184, 139, 203, 245, 9, 234, 110, 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