Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b61a13d0b896c8e74f70f86ad33191f6b640f892a651a4f48086326ee92bfa

Tx prefix hash: 618dab322f57f8052e8ef343acc918d22f80108e397fae819a49e6b92d70bf19
Tx public key: e6282a4baa8259a7e36b7802606418d90925b92f71d869b3b807a4e8c28b9c52
Timestamp: 1701018576 Timestamp [UCT]: 2023-11-26 17:09:36 Age [y:d:h:m:s]: 01:050:23:11:34
Block: 900192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297798 RingCT/type: yes/0
Extra: 01e6282a4baa8259a7e36b7802606418d90925b92f71d869b3b807a4e8c28b9c5202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.638690122000 dcy

stealth address amount amount idx
00: ed941089c5cabfefa21665ac4830fd15ef6713ed828d05120076fc2479c15685 0.638690122000 1356673 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": 900202, "vin": [ { "gen": { "height": 900192 } } ], "vout": [ { "amount": 638690122, "target": { "key": "ed941089c5cabfefa21665ac4830fd15ef6713ed828d05120076fc2479c15685" } } ], "extra": [ 1, 230, 40, 42, 75, 170, 130, 89, 167, 227, 107, 120, 2, 96, 100, 24, 217, 9, 37, 185, 47, 113, 216, 105, 179, 184, 7, 164, 232, 194, 139, 156, 82, 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