Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c35646a0161c1a26411db5ee14aed3228a327f9da3a45c963d977e7ba5f59532

Tx prefix hash: 09a9d071d89dbe7525a385368fce7f1e4bf2f910b60a8806a117a147cd8d4bd4
Tx public key: 212e5f8058d5a0febc81d57ce535698f6a6665243bb84ed40f043963dea7ccbe
Timestamp: 1733566318 Timestamp [UCT]: 2024-12-07 10:11:58 Age [y:d:h:m:s]: 00:112:03:46:01
Block: 1169927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79946 RingCT/type: yes/0
Extra: 01212e5f8058d5a0febc81d57ce535698f6a6665243bb84ed40f043963dea7ccbe021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2b051aed12a3a15efb8d1a345c89a45177a0364caffce07a0291ebd1fcd4a0d 0.600000000000 1655652 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": 1169937, "vin": [ { "gen": { "height": 1169927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2b051aed12a3a15efb8d1a345c89a45177a0364caffce07a0291ebd1fcd4a0d" } } ], "extra": [ 1, 33, 46, 95, 128, 88, 213, 160, 254, 188, 129, 213, 124, 229, 53, 105, 143, 106, 102, 101, 36, 59, 184, 78, 212, 15, 4, 57, 99, 222, 167, 204, 190, 2, 17, 0, 0, 0, 9, 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