Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5304a449bb0d85ea86914c39c7e07fb6a77cb5c53367af6c95090e4df984d86

Tx prefix hash: 835a94bae7306707ea88d40a6a36e52d33ae95284a6e0de9d93277078275c765
Tx public key: 7476863d1a116153093b6857c70f0e32b0a768c67f51ca522e4c85701af76814
Timestamp: 1701169067 Timestamp [UCT]: 2023-11-28 10:57:47 Age [y:d:h:m:s]: 00:363:08:50:00
Block: 901438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260181 RingCT/type: yes/0
Extra: 017476863d1a116153093b6857c70f0e32b0a768c67f51ca522e4c85701af7681402110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.632647334000 dcy

stealth address amount amount idx
00: 6198c7f03239809a4404ec3cc6c1f7722f660c5d60fe968cebcdc2d92823de5b 0.632647334000 1358001 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": 901448, "vin": [ { "gen": { "height": 901438 } } ], "vout": [ { "amount": 632647334, "target": { "key": "6198c7f03239809a4404ec3cc6c1f7722f660c5d60fe968cebcdc2d92823de5b" } } ], "extra": [ 1, 116, 118, 134, 61, 26, 17, 97, 83, 9, 59, 104, 87, 199, 15, 14, 50, 176, 167, 104, 198, 127, 81, 202, 82, 46, 76, 133, 112, 26, 247, 104, 20, 2, 17, 0, 0, 0, 12, 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