Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd687aecd4e74b08b46b815c60d152644ac681a82a55272728ed10dbf94815b

Tx prefix hash: 1b953abc40b80ceb3e953c5c415ea07aa3b2fee068617f9c5c84d902be00948e
Tx public key: 4240667092f152fa36538c7144511d986def7b7e782b30a8e66340efb7f5f9a9
Timestamp: 1722464330 Timestamp [UCT]: 2024-07-31 22:18:50 Age [y:d:h:m:s]: 00:260:20:05:18
Block: 1077981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186339 RingCT/type: yes/0
Extra: 014240667092f152fa36538c7144511d986def7b7e782b30a8e66340efb7f5f9a9021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b2f7b02c0132fe03213def9c4652c4754a28c7204ebfedfbcc1878d77059074 0.600000000000 1550536 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": 1077991, "vin": [ { "gen": { "height": 1077981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2f7b02c0132fe03213def9c4652c4754a28c7204ebfedfbcc1878d77059074" } } ], "extra": [ 1, 66, 64, 102, 112, 146, 241, 82, 250, 54, 83, 140, 113, 68, 81, 29, 152, 109, 239, 123, 126, 120, 43, 48, 168, 230, 99, 64, 239, 183, 245, 249, 169, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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