Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d932d3b1f4050953d5de379752a4175436f76d6ff67e57025395686df16286e3

Tx prefix hash: 963d8fc0378e13f6ccc72e21eadd42dda39b93cfd03477d19e872fafe224562a
Tx public key: 888ef24cc37d3548bdec7b34412329b3c185c72411f061ce32999ad3b1b715bd
Timestamp: 1738293909 Timestamp [UCT]: 2025-01-31 03:25:09 Age [y:d:h:m:s]: 00:319:10:01:30
Block: 1208802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226080 RingCT/type: yes/0
Extra: 01888ef24cc37d3548bdec7b34412329b3c185c72411f061ce32999ad3b1b715bd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7c482d8e2cef8a4fde00f8915f9d8c5d9fad9451d984dad2b7e9f00774210d 0.600000000000 1695537 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": 1208812, "vin": [ { "gen": { "height": 1208802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7c482d8e2cef8a4fde00f8915f9d8c5d9fad9451d984dad2b7e9f00774210d" } } ], "extra": [ 1, 136, 142, 242, 76, 195, 125, 53, 72, 189, 236, 123, 52, 65, 35, 41, 179, 193, 133, 199, 36, 17, 240, 97, 206, 50, 153, 154, 211, 177, 183, 21, 189, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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