Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 485b368be7bf0081229f6baeea68d21ecec2eb47d1596bf2c2b70fb118238a5a

Tx prefix hash: 183c7ae7809cccecb1846baacbe4b5227d7f0fb8fb24a364f2b14e9e68c7e387
Tx public key: 549b6c416ed1ec16316d0778d5f4c863c785edf28ab80d6bfcb3c3dc82bfd212
Timestamp: 1729743969 Timestamp [UCT]: 2024-10-24 04:26:09 Age [y:d:h:m:s]: 01:026:09:48:03
Block: 1138305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277266 RingCT/type: yes/0
Extra: 01549b6c416ed1ec16316d0778d5f4c863c785edf28ab80d6bfcb3c3dc82bfd2120211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a9643601d59be3a32b121e7e05595c17ce17a7b346591e3079412664fd98330 0.600000000000 1621936 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": 1138315, "vin": [ { "gen": { "height": 1138305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a9643601d59be3a32b121e7e05595c17ce17a7b346591e3079412664fd98330" } } ], "extra": [ 1, 84, 155, 108, 65, 110, 209, 236, 22, 49, 109, 7, 120, 213, 244, 200, 99, 199, 133, 237, 242, 138, 184, 13, 107, 252, 179, 195, 220, 130, 191, 210, 18, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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