Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5edefb79e16683f79868be5804be6d67b67ed953434de04ff0cfd4aa580f62

Tx prefix hash: 1cde5898a88506cbc0e778022b4cb6d2fa4d2e34c330d19ae3298cdfd75b2db2
Tx public key: 592dc8e9678ebb11ef7403b7968d69d47ffeaebd8975c3f9e0c0bda16c9cd731
Timestamp: 1709103058 Timestamp [UCT]: 2024-02-28 06:50:58 Age [y:d:h:m:s]: 01:282:14:31:05
Block: 967226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460727 RingCT/type: yes/0
Extra: 01592dc8e9678ebb11ef7403b7968d69d47ffeaebd8975c3f9e0c0bda16c9cd7310211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e615021c7e175b680ffee3b66b79d2c22f34fafd45316444371541854ad15e37 0.600000000000 1426997 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": 967236, "vin": [ { "gen": { "height": 967226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e615021c7e175b680ffee3b66b79d2c22f34fafd45316444371541854ad15e37" } } ], "extra": [ 1, 89, 45, 200, 233, 103, 142, 187, 17, 239, 116, 3, 183, 150, 141, 105, 212, 127, 254, 174, 189, 137, 117, 195, 249, 224, 192, 189, 161, 108, 156, 215, 49, 2, 17, 0, 0, 0, 7, 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