Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e0e554bb706a15de9f0a7d828ff4eb337942f3e3644190c8e555ebe07c28ceb

Tx prefix hash: dfa45fb4fa07ddc6fd561a36b15395fd6cb2cfabb8611bcaf231dafba1a049fd
Tx public key: b3fd553a30fc7e2b38e56fb7ae824af42a4b3fc3e7d32d9fd269a7f00a0828cc
Timestamp: 1733648907 Timestamp [UCT]: 2024-12-08 09:08:27 Age [y:d:h:m:s]: 00:146:01:00:29
Block: 1170614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104186 RingCT/type: yes/0
Extra: 01b3fd553a30fc7e2b38e56fb7ae824af42a4b3fc3e7d32d9fd269a7f00a0828cc021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07c6826f4931225a472a543468e26505e217718d9ff3ba92434429e37ae6db0f 0.600000000000 1656345 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": 1170624, "vin": [ { "gen": { "height": 1170614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07c6826f4931225a472a543468e26505e217718d9ff3ba92434429e37ae6db0f" } } ], "extra": [ 1, 179, 253, 85, 58, 48, 252, 126, 43, 56, 229, 111, 183, 174, 130, 74, 244, 42, 75, 63, 195, 231, 211, 45, 159, 210, 105, 167, 240, 10, 8, 40, 204, 2, 17, 0, 0, 0, 7, 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