Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23e84662aa687f72b825df91dd578e91912dd7c72c109ff67b8e74604ee3af0

Tx prefix hash: f18a1a8d38aed92f5d46daf18a759fa503a704dd206ce5b624672bee1db349c1
Tx public key: d8b85859ab4a20c4454e74af231d2961776a033e6535f4bb7635a1a1b7ee0af5
Timestamp: 1716697797 Timestamp [UCT]: 2024-05-26 04:29:57 Age [y:d:h:m:s]: 00:342:04:06:59
Block: 1030183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244575 RingCT/type: yes/0
Extra: 01d8b85859ab4a20c4454e74af231d2961776a033e6535f4bb7635a1a1b7ee0af50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24f34d8226306cc56db4bc6010111790c3f349efd8f938b50dfe1a16335841f8 0.600000000000 1498436 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": 1030193, "vin": [ { "gen": { "height": 1030183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24f34d8226306cc56db4bc6010111790c3f349efd8f938b50dfe1a16335841f8" } } ], "extra": [ 1, 216, 184, 88, 89, 171, 74, 32, 196, 69, 78, 116, 175, 35, 29, 41, 97, 119, 106, 3, 62, 101, 53, 244, 187, 118, 53, 161, 161, 183, 238, 10, 245, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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