Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e2d4d665140e3c984edcb17a3f3ca7472d21ac6122c91760245e745c2a0b59

Tx prefix hash: 83ba8a27a8b3368f2a5fb36148b83f1ca1ff7c70cff5bfc87597fb6b5e7642a8
Tx public key: 138588f80c0cc953f1ae8be36ef1012e1ff9c5f93d6c2f795be1fde1b1b9ba4d
Timestamp: 1710225540 Timestamp [UCT]: 2024-03-12 06:39:00 Age [y:d:h:m:s]: 00:356:17:57:46
Block: 976531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255065 RingCT/type: yes/0
Extra: 01138588f80c0cc953f1ae8be36ef1012e1ff9c5f93d6c2f795be1fde1b1b9ba4d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a7b5737574a626bf5d08af44be7714c426cca20dcaf8f77bc74a3e00eaa4bf2 0.600000000000 1436526 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": 976541, "vin": [ { "gen": { "height": 976531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a7b5737574a626bf5d08af44be7714c426cca20dcaf8f77bc74a3e00eaa4bf2" } } ], "extra": [ 1, 19, 133, 136, 248, 12, 12, 201, 83, 241, 174, 139, 227, 110, 241, 1, 46, 31, 249, 197, 249, 61, 108, 47, 121, 91, 225, 253, 225, 177, 185, 186, 77, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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