Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c3d049f26962007c34a27786b41ec46a3426968adb898e7d03c77c22c8c6e3

Tx prefix hash: a2ec010e95cc0c309db0c25b18e8339d46886cd41fc7b6415eeadd2071db4051
Tx public key: a860ef49d4cb10097aec87e5dd665cbd4f9aa148f1f2250ba41515f5d8afc3e9
Timestamp: 1705780762 Timestamp [UCT]: 2024-01-20 19:59:22 Age [y:d:h:m:s]: 01:319:19:48:36
Block: 939630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487439 RingCT/type: yes/0
Extra: 01a860ef49d4cb10097aec87e5dd665cbd4f9aa148f1f2250ba41515f5d8afc3e90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 400b043e670b423c535f6922396dd057d5acaf2256ae1109ad1f44a7e6c2708e 0.600000000000 1397740 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": 939640, "vin": [ { "gen": { "height": 939630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "400b043e670b423c535f6922396dd057d5acaf2256ae1109ad1f44a7e6c2708e" } } ], "extra": [ 1, 168, 96, 239, 73, 212, 203, 16, 9, 122, 236, 135, 229, 221, 102, 92, 189, 79, 154, 161, 72, 241, 242, 37, 11, 164, 21, 21, 245, 216, 175, 195, 233, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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