Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd67baecd0da4c21e394298b3a334e8e9c9bac9436ec13eb8c7d2a25c995ed6b

Tx prefix hash: b00276ac0766345c42e7360f2bfddb5deeea2f90929527d3050337a4efb309fb
Tx public key: 4a860eb8e38b380406fc086be6a0c8680c9280f1d4e87422784d3ee48dbc8321
Timestamp: 1733532026 Timestamp [UCT]: 2024-12-07 00:40:26 Age [y:d:h:m:s]: 00:138:10:27:45
Block: 1169639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98751 RingCT/type: yes/0
Extra: 014a860eb8e38b380406fc086be6a0c8680c9280f1d4e87422784d3ee48dbc8321021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7080d35227a41e22c89cbc793976ca4a80733a31b3f4c93db63ff5c226e2ac 0.600000000000 1655360 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": 1169649, "vin": [ { "gen": { "height": 1169639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7080d35227a41e22c89cbc793976ca4a80733a31b3f4c93db63ff5c226e2ac" } } ], "extra": [ 1, 74, 134, 14, 184, 227, 139, 56, 4, 6, 252, 8, 107, 230, 160, 200, 104, 12, 146, 128, 241, 212, 232, 116, 34, 120, 77, 62, 228, 141, 188, 131, 33, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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