Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f32a84a7e80fb550853dd7dd4d9b083dfb8005a0e984788df380ce26b8b02a1

Tx prefix hash: 0f30df63ddd3889d001d54e24b4b89a1aad48d769035a021784f6ae836a44597
Tx public key: 3181d5a2e9fefd8698261df10fdfb9f6bdd11a17d05dd2cf2452502a0a387f57
Timestamp: 1697458869 Timestamp [UCT]: 2023-10-16 12:21:09 Age [y:d:h:m:s]: 01:197:01:35:08
Block: 870878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401887 RingCT/type: yes/0
Extra: 013181d5a2e9fefd8698261df10fdfb9f6bdd11a17d05dd2cf2452502a0a387f57021100000003faf35c9c000000000000000000

1 output(s) for total of 0.798766226000 dcy

stealth address amount amount idx
00: bf82b2756fcca92779ec82c186021ca9dd4a5dcffa8ada1a470611c9605526ed 0.798766226000 1325833 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": 870888, "vin": [ { "gen": { "height": 870878 } } ], "vout": [ { "amount": 798766226, "target": { "key": "bf82b2756fcca92779ec82c186021ca9dd4a5dcffa8ada1a470611c9605526ed" } } ], "extra": [ 1, 49, 129, 213, 162, 233, 254, 253, 134, 152, 38, 29, 241, 15, 223, 185, 246, 189, 209, 26, 23, 208, 93, 210, 207, 36, 82, 80, 42, 10, 56, 127, 87, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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