Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b18258889ee869065da87a3d23b728cae883b2bda5877241e38b627ea27c27

Tx prefix hash: c4fa20b54c5d5489a738596ab8a1c7632113dd5177035689e3864d4dfca0643b
Tx public key: e9d4c0f28477a149758b270ecdbd6d77c03c6cb044b136f4534def96517e5b1d
Timestamp: 1707794298 Timestamp [UCT]: 2024-02-13 03:18:18 Age [y:d:h:m:s]: 01:267:04:15:32
Block: 956361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449692 RingCT/type: yes/0
Extra: 01e9d4c0f28477a149758b270ecdbd6d77c03c6cb044b136f4534def96517e5b1d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 892bd8b0b6122cf8fbe02334e08d08f85fde35634e8936eba2cba8dafa253e28 0.600000000000 1415665 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": 956371, "vin": [ { "gen": { "height": 956361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "892bd8b0b6122cf8fbe02334e08d08f85fde35634e8936eba2cba8dafa253e28" } } ], "extra": [ 1, 233, 212, 192, 242, 132, 119, 161, 73, 117, 139, 39, 14, 205, 189, 109, 119, 192, 60, 108, 176, 68, 177, 54, 244, 83, 77, 239, 150, 81, 126, 91, 29, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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