Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a3e95da4babcaa1cbcef7f971c12198a4c11eb3751f6ad6c9b7ba5e54347d05

Tx prefix hash: 6d6b837f92158eca8050d8f93090ccd6be062b8eb7bc1de71c375b89ce51c2f9
Tx public key: 9eb67b1a8f6e86be61ba205996934bee771e5f0df1931c7397f11aa353ba5861
Timestamp: 1723633034 Timestamp [UCT]: 2024-08-14 10:57:14 Age [y:d:h:m:s]: 00:225:19:43:32
Block: 1087676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161264 RingCT/type: yes/0
Extra: 019eb67b1a8f6e86be61ba205996934bee771e5f0df1931c7397f11aa353ba5861021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cfe4f9b3cd107a3e435ef2ef8439aaca515b38ab09ebf54fa3d32cee8f0f3f9b 0.600000000000 1562287 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": 1087686, "vin": [ { "gen": { "height": 1087676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfe4f9b3cd107a3e435ef2ef8439aaca515b38ab09ebf54fa3d32cee8f0f3f9b" } } ], "extra": [ 1, 158, 182, 123, 26, 143, 110, 134, 190, 97, 186, 32, 89, 150, 147, 75, 238, 119, 30, 95, 13, 241, 147, 28, 115, 151, 241, 26, 163, 83, 186, 88, 97, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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