Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0386be8c4848918c28d20896b93808e9d1ed0d033d4710204652fb61d07833c0

Tx prefix hash: 5765bffe19eecdeff133e255558ec6670e19efbb17a3a31d96301fc10aecfdbb
Tx public key: a1dfc797fcf436e50eadfb2236ff52e4f6c526e1e07be6eaf7c7d316d4215069
Timestamp: 1730790537 Timestamp [UCT]: 2024-11-05 07:08:57 Age [y:d:h:m:s]: 01:004:01:37:33
Block: 1146929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261321 RingCT/type: yes/0
Extra: 01a1dfc797fcf436e50eadfb2236ff52e4f6c526e1e07be6eaf7c7d316d4215069021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3798c923eb74b3402d6b6b78aeca3063460a402d1c53a1a8bd79ce906dc78e19 0.600000000000 1631622 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": 1146939, "vin": [ { "gen": { "height": 1146929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3798c923eb74b3402d6b6b78aeca3063460a402d1c53a1a8bd79ce906dc78e19" } } ], "extra": [ 1, 161, 223, 199, 151, 252, 244, 54, 229, 14, 173, 251, 34, 54, 255, 82, 228, 246, 197, 38, 225, 224, 123, 230, 234, 247, 199, 211, 22, 212, 33, 80, 105, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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