Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67853226e352ebdb404d2f0b8f16555aa303cbe04a2862def3c3fa15ab6627d9

Tx prefix hash: d8b7de200446f0f9f72257120d0d45731e5ebd27dfdb9a2cbd8965bd9457a6be
Tx public key: a38f76f6a12a932e3570474121765b319c6b4981cec952cf159eeec1794e193d
Timestamp: 1711303530 Timestamp [UCT]: 2024-03-24 18:05:30 Age [y:d:h:m:s]: 01:083:18:49:58
Block: 985481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320770 RingCT/type: yes/0
Extra: 01a38f76f6a12a932e3570474121765b319c6b4981cec952cf159eeec1794e193d02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1b5ec308fb769607634aee5cd5c8a37e26e37c08eec55476badda0a75871f5e 0.600000000000 1445694 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": 985491, "vin": [ { "gen": { "height": 985481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1b5ec308fb769607634aee5cd5c8a37e26e37c08eec55476badda0a75871f5e" } } ], "extra": [ 1, 163, 143, 118, 246, 161, 42, 147, 46, 53, 112, 71, 65, 33, 118, 91, 49, 156, 107, 73, 129, 206, 201, 82, 207, 21, 158, 238, 193, 121, 78, 25, 61, 2, 17, 0, 0, 0, 11, 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