Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed18c8e7c38dbc018860f66191b88fce1c487de23b1e19a314335767f4c2ee0d

Tx prefix hash: e5eebcfe8ab80f5de4ec51d4778980f45a116859c396ff2b3142ddee2b9e84b8
Tx public key: a7ae2051b0dd82519b0a83f3066e89d30a9c2bee17a162439b44d2a6b5bfc072
Timestamp: 1696867665 Timestamp [UCT]: 2023-10-09 16:07:45 Age [y:d:h:m:s]: 01:167:17:17:52
Block: 865990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380888 RingCT/type: yes/0
Extra: 01a7ae2051b0dd82519b0a83f3066e89d30a9c2bee17a162439b44d2a6b5bfc07202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.829116721000 dcy

stealth address amount amount idx
00: 8027d0d23c5c96581ad3dc49acaf7b4583d6f27dd03349b70b6d353a8813af2a 0.829116721000 1320556 of 0

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": 866000, "vin": [ { "gen": { "height": 865990 } } ], "vout": [ { "amount": 829116721, "target": { "key": "8027d0d23c5c96581ad3dc49acaf7b4583d6f27dd03349b70b6d353a8813af2a" } } ], "extra": [ 1, 167, 174, 32, 81, 176, 221, 130, 81, 155, 10, 131, 243, 6, 110, 137, 211, 10, 156, 43, 238, 23, 161, 98, 67, 155, 68, 210, 166, 181, 191, 192, 114, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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