Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6819aa1ad034850390c22910b0a1ecdfc6a04777afe66f518daba7cb866c508c

Tx prefix hash: d9a147408bbf9c121933d13191b418854e8735767ca41734527e1640794e2c7f
Tx public key: 603fccd2f6a5c6332b70833ab3d9ac39aa99cbd823d87add3d7a9e79be3fa17a
Timestamp: 1730943970 Timestamp [UCT]: 2024-11-07 01:46:10 Age [y:d:h:m:s]: 00:017:12:06:18
Block: 1148202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12530 RingCT/type: yes/0
Extra: 01603fccd2f6a5c6332b70833ab3d9ac39aa99cbd823d87add3d7a9e79be3fa17a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f93619fffcb6a1cc15213de3eae51af77bc994a76b5a5f4f245fbedc767780b 0.600000000000 1632997 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": 1148212, "vin": [ { "gen": { "height": 1148202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f93619fffcb6a1cc15213de3eae51af77bc994a76b5a5f4f245fbedc767780b" } } ], "extra": [ 1, 96, 63, 204, 210, 246, 165, 198, 51, 43, 112, 131, 58, 179, 217, 172, 57, 170, 153, 203, 216, 35, 216, 122, 221, 61, 122, 158, 121, 190, 63, 161, 122, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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