Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5801331e386c464a45e94d65b1995e2ddde961f4c3bbc710de8267e56d08f52b

Tx prefix hash: 70a89a63d0ca8254e4c7c44b5ef7cb20e6c91306ff809998e91d9d19d66dd7f4
Tx public key: e9214670e4365efd421a1bb6b46dd0b8a63254e3721541d2792decff9b247a08
Timestamp: 1677235335 Timestamp [UCT]: 2023-02-24 10:42:15 Age [y:d:h:m:s]: 02:001:21:18:24
Block: 703896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522900 RingCT/type: yes/0
Extra: 01e9214670e4365efd421a1bb6b46dd0b8a63254e3721541d2792decff9b247a0802110000000674b6d784000000000000000000

1 output(s) for total of 2.855618971000 dcy

stealth address amount amount idx
00: eb3ffbf365909716c2d95598eee060c445cca4581a9bdda8413f7d519c7f6716 2.855618971000 1147525 of 0

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": 703906, "vin": [ { "gen": { "height": 703896 } } ], "vout": [ { "amount": 2855618971, "target": { "key": "eb3ffbf365909716c2d95598eee060c445cca4581a9bdda8413f7d519c7f6716" } } ], "extra": [ 1, 233, 33, 70, 112, 228, 54, 94, 253, 66, 26, 27, 182, 180, 109, 208, 184, 166, 50, 84, 227, 114, 21, 65, 210, 121, 45, 236, 255, 155, 36, 122, 8, 2, 17, 0, 0, 0, 6, 116, 182, 215, 132, 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