Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba41b0742663dc479663b06201c7d0aae73746e4f43c47d883d76b4b8e1cb1c

Tx prefix hash: 8bf2ad03a4eab7c2c7207e659405289f71eb990b3653f899e32d13cb2cd20e81
Tx public key: 0a2c16134fa5570b2cf1067ea8ea8ef983613936684aaf99de40acd3f378baf3
Timestamp: 1721083024 Timestamp [UCT]: 2024-07-15 22:37:04 Age [y:d:h:m:s]: 00:293:23:16:18
Block: 1066546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210025 RingCT/type: yes/0
Extra: 010a2c16134fa5570b2cf1067ea8ea8ef983613936684aaf99de40acd3f378baf3021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e17cae01feba791e96a17cfa54bdc9591920b6bdd27a40ef864eb0b4e101a6c1 0.600000000000 1537205 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": 1066556, "vin": [ { "gen": { "height": 1066546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e17cae01feba791e96a17cfa54bdc9591920b6bdd27a40ef864eb0b4e101a6c1" } } ], "extra": [ 1, 10, 44, 22, 19, 79, 165, 87, 11, 44, 241, 6, 126, 168, 234, 142, 249, 131, 97, 57, 54, 104, 74, 175, 153, 222, 64, 172, 211, 243, 120, 186, 243, 2, 17, 0, 0, 0, 7, 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