Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bac66720cbb5fc479e018de82837f1b137f39ac37a5f8e4370af3348d4ae918

Tx prefix hash: 39724ba38bb1fab8cbc67003b48e77757247ab0a1fa1472ef698985f1df3338f
Tx public key: 40b05b2eed41e1f6237bd2e986c2fe37dc1be16ba7410db9c022b445e09054dc
Timestamp: 1718595791 Timestamp [UCT]: 2024-06-17 03:43:11 Age [y:d:h:m:s]: 00:220:20:46:29
Block: 1045910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158012 RingCT/type: yes/0
Extra: 0140b05b2eed41e1f6237bd2e986c2fe37dc1be16ba7410db9c022b445e09054dc02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebe5fc61423351394af9d7a0e76a7b5ac1fb1b49c55e22e0f4eb7bacc87e1ec0 0.600000000000 1515621 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": 1045920, "vin": [ { "gen": { "height": 1045910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebe5fc61423351394af9d7a0e76a7b5ac1fb1b49c55e22e0f4eb7bacc87e1ec0" } } ], "extra": [ 1, 64, 176, 91, 46, 237, 65, 225, 246, 35, 123, 210, 233, 134, 194, 254, 55, 220, 27, 225, 107, 167, 65, 13, 185, 192, 34, 180, 69, 224, 144, 84, 220, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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