Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc062e144d0f8b5411a0f0683b3dcfb5f24e46516fcd74c38d5fd93b63306d3

Tx prefix hash: 254a4eeb643eb4902a3b2e3dbf96f4c37b1913a991ace07e9ddbe5fb951511fe
Tx public key: 8ff8a456e2fb1d09d314352bb192a3b1c479cf59e151cc85e3a92272b6c8f33d
Timestamp: 1722454532 Timestamp [UCT]: 2024-07-31 19:35:32 Age [y:d:h:m:s]: 00:324:00:54:16
Block: 1077891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231385 RingCT/type: yes/0
Extra: 018ff8a456e2fb1d09d314352bb192a3b1c479cf59e151cc85e3a92272b6c8f33d021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 898f40449bc5ce274365a4b9556fde8450e3107a9e3d011bcb574a2f009b5d5a 0.600000000000 1550446 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": 1077901, "vin": [ { "gen": { "height": 1077891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "898f40449bc5ce274365a4b9556fde8450e3107a9e3d011bcb574a2f009b5d5a" } } ], "extra": [ 1, 143, 248, 164, 86, 226, 251, 29, 9, 211, 20, 53, 43, 177, 146, 163, 177, 196, 121, 207, 89, 225, 81, 204, 133, 227, 169, 34, 114, 182, 200, 243, 61, 2, 17, 0, 0, 0, 8, 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