Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dd82f76f5a30cabf30debe88d3c5d246f2fee11d817c40e53941350b1f9bf5e

Tx prefix hash: fd3ee6d022aa3c05e572713ae382c7989f3f0bb443fc35bbb2fc4cc69f1da8ef
Tx public key: 834c975e812f5801a6716c66243225a10350422031f08b825312f619389d3bf5
Timestamp: 1729609638 Timestamp [UCT]: 2024-10-22 15:07:18 Age [y:d:h:m:s]: 00:196:05:06:03
Block: 1137185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140065 RingCT/type: yes/0
Extra: 01834c975e812f5801a6716c66243225a10350422031f08b825312f619389d3bf5021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ec244bc7a5fd58e48ee08ac0859972c28589ab10b76a5a7ebc3a4e2bf5fd700 0.600000000000 1620630 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": 1137195, "vin": [ { "gen": { "height": 1137185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ec244bc7a5fd58e48ee08ac0859972c28589ab10b76a5a7ebc3a4e2bf5fd700" } } ], "extra": [ 1, 131, 76, 151, 94, 129, 47, 88, 1, 166, 113, 108, 102, 36, 50, 37, 161, 3, 80, 66, 32, 49, 240, 139, 130, 83, 18, 246, 25, 56, 157, 59, 245, 2, 17, 0, 0, 0, 5, 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