Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ee0f2110df1c48fc232ed3cfe4564db0bb9d6489f9e04028ceed3d5ef20567

Tx prefix hash: 7b708aebbfe7fe2b921e3617fba35d35a90dace6f292c83da2543da10d27c7b5
Tx public key: 1987d7397c3f846bb2ed8a6cfddd0f12c3d87e1f13e06c81c6cae0b9d765ad1c
Timestamp: 1700774029 Timestamp [UCT]: 2023-11-23 21:13:49 Age [y:d:h:m:s]: 01:092:10:50:29
Block: 898154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327207 RingCT/type: yes/0
Extra: 011987d7397c3f846bb2ed8a6cfddd0f12c3d87e1f13e06c81c6cae0b9d765ad1c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.648698573000 dcy

stealth address amount amount idx
00: a4490b7253568a1ef68f0d1186bcc59a9f9a9ca722203b36af8042fd9d02bbca 0.648698573000 1354559 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": 898164, "vin": [ { "gen": { "height": 898154 } } ], "vout": [ { "amount": 648698573, "target": { "key": "a4490b7253568a1ef68f0d1186bcc59a9f9a9ca722203b36af8042fd9d02bbca" } } ], "extra": [ 1, 25, 135, 215, 57, 124, 63, 132, 107, 178, 237, 138, 108, 253, 221, 15, 18, 195, 216, 126, 31, 19, 224, 108, 129, 198, 202, 224, 185, 215, 101, 173, 28, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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