Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ec6ce2068b5c57797caa4ca077227e3c142f0c211bf03a1f45bd00f0cde992

Tx prefix hash: 83b2f0d3b2eec586bb5a6e95490385c685ea3ba1329c03fb36258560a24fb1b2
Tx public key: d2daf1df744244e83c3a3c1c103b7509ba9ba138b6763e27ed39e066539b144d
Timestamp: 1731579024 Timestamp [UCT]: 2024-11-14 10:10:24 Age [y:d:h:m:s]: 00:166:08:51:19
Block: 1153459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118749 RingCT/type: yes/0
Extra: 01d2daf1df744244e83c3a3c1c103b7509ba9ba138b6763e27ed39e066539b144d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f01ac78e31df0ca4473bbac96c7ea2461ec9bfbb17a525c6214247f3193a93 0.600000000000 1639068 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": 1153469, "vin": [ { "gen": { "height": 1153459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f01ac78e31df0ca4473bbac96c7ea2461ec9bfbb17a525c6214247f3193a93" } } ], "extra": [ 1, 210, 218, 241, 223, 116, 66, 68, 232, 60, 58, 60, 28, 16, 59, 117, 9, 186, 155, 161, 56, 182, 118, 62, 39, 237, 57, 224, 102, 83, 155, 20, 77, 2, 17, 0, 0, 0, 2, 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