Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea08fe0085701d964b2c64300aafb96ea906d107454d20448c5c149647985891

Tx prefix hash: 795978156c9649ae4ca7e230bc4fea7a730eef1ac0407c4349f01513fab7e2e7
Tx public key: 42a6d2b6d7235df91d2e9fab7534f08fbd8879bbfbca7ded4371ae505d32f9d3
Timestamp: 1717330134 Timestamp [UCT]: 2024-06-02 12:08:54 Age [y:d:h:m:s]: 01:164:21:24:39
Block: 1035429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376432 RingCT/type: yes/0
Extra: 0142a6d2b6d7235df91d2e9fab7534f08fbd8879bbfbca7ded4371ae505d32f9d302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d185a07b814403130dcd000adf9e500c1fcba49269ede5a64a4b642984b653 0.600000000000 1503950 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": 1035439, "vin": [ { "gen": { "height": 1035429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d185a07b814403130dcd000adf9e500c1fcba49269ede5a64a4b642984b653" } } ], "extra": [ 1, 66, 166, 210, 182, 215, 35, 93, 249, 29, 46, 159, 171, 117, 52, 240, 143, 189, 136, 121, 187, 251, 202, 125, 237, 67, 113, 174, 80, 93, 50, 249, 211, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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