Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3183887e0f97697ffdfebf546928b04fd07617130a97ac2b862d3548b4ace0

Tx prefix hash: dc9bdbff5012f82c72e70726f9845ea243b87457047945b8b28ae3e5603ecacc
Tx public key: acea4c17c490abc95167f0fae91dea1cb7cadd8557d63168efa2eca3f5f03f1b
Timestamp: 1714674995 Timestamp [UCT]: 2024-05-02 18:36:35 Age [y:d:h:m:s]: 00:300:21:52:36
Block: 1013416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215072 RingCT/type: yes/0
Extra: 01acea4c17c490abc95167f0fae91dea1cb7cadd8557d63168efa2eca3f5f03f1b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ffcb7078b1335ed4e94bf6c96d038cc7230a1ae45d4b01ab0c81f4e94aeb7ab 0.600000000000 1476227 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": 1013426, "vin": [ { "gen": { "height": 1013416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ffcb7078b1335ed4e94bf6c96d038cc7230a1ae45d4b01ab0c81f4e94aeb7ab" } } ], "extra": [ 1, 172, 234, 76, 23, 196, 144, 171, 201, 81, 103, 240, 250, 233, 29, 234, 28, 183, 202, 221, 133, 87, 214, 49, 104, 239, 162, 236, 163, 245, 240, 63, 27, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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