Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4252a33d31373b24daf7649c7bc8ce25bd19e4dda7e7e7ce1fe88b48371edee

Tx prefix hash: cd1a50f2e7024675564880a3c5b15ebd40322ecd1c8674e2e69b86c468d33180
Tx public key: 2c84b25bb506d3fc6344715a5b88db8ed0fca5a74d64c1586cfcd71c161043af
Timestamp: 1723055750 Timestamp [UCT]: 2024-08-07 18:35:50 Age [y:d:h:m:s]: 01:093:06:22:50
Block: 1082884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325134 RingCT/type: yes/0
Extra: 012c84b25bb506d3fc6344715a5b88db8ed0fca5a74d64c1586cfcd71c161043af021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec46a1f4a252b551b9f35c2bb08455128a68b060024c2983c31a9e3ed2b3dca 0.600000000000 1556719 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": 1082894, "vin": [ { "gen": { "height": 1082884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec46a1f4a252b551b9f35c2bb08455128a68b060024c2983c31a9e3ed2b3dca" } } ], "extra": [ 1, 44, 132, 178, 91, 181, 6, 211, 252, 99, 68, 113, 90, 91, 136, 219, 142, 208, 252, 165, 167, 77, 100, 193, 88, 108, 252, 215, 28, 22, 16, 67, 175, 2, 17, 0, 0, 0, 1, 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