Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52ac185d9fb2c75b206ef7ebe60a5ba1087bc1c198a0881ce9ce3f84929315c

Tx prefix hash: a5d987d4a12654eb05bbc041d31846f76eb0b7e134e3309e8da0c0101cc817a4
Tx public key: 4746040253e52780c65e9c1375573a244519ba4222d33d1da05f0c24e392d22b
Timestamp: 1695476663 Timestamp [UCT]: 2023-09-23 13:44:23 Age [y:d:h:m:s]: 01:158:22:41:43
Block: 854444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374633 RingCT/type: yes/0
Extra: 014746040253e52780c65e9c1375573a244519ba4222d33d1da05f0c24e392d22b02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.905466488000 dcy

stealth address amount amount idx
00: bc1fb6c44b53893286350626defad583ca461f0f7c7d04d4f1f87516248db645 0.905466488000 1308416 of 0

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": 854454, "vin": [ { "gen": { "height": 854444 } } ], "vout": [ { "amount": 905466488, "target": { "key": "bc1fb6c44b53893286350626defad583ca461f0f7c7d04d4f1f87516248db645" } } ], "extra": [ 1, 71, 70, 4, 2, 83, 229, 39, 128, 198, 94, 156, 19, 117, 87, 58, 36, 69, 25, 186, 66, 34, 211, 61, 29, 160, 95, 12, 36, 227, 146, 210, 43, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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