Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbafb4d740cbf9ca8fcf88a452153d13e373f7fbaaa04b87d1d37687f39e59ce

Tx prefix hash: 16770d24fa55e2f61f6bf8609a45e17a9f76e97091647450ce2f9a286392ba29
Tx public key: a45fdba9f89d0bccd5e76274e895a084301bf105ef747b2b2a2db719dfe9c55a
Timestamp: 1672853524 Timestamp [UCT]: 2023-01-04 17:32:04 Age [y:d:h:m:s]: 02:108:11:35:22
Block: 667556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599216 RingCT/type: yes/0
Extra: 01a45fdba9f89d0bccd5e76274e895a084301bf105ef747b2b2a2db719dfe9c55a02110000000ce6d27f9c000000000000000000

1 output(s) for total of 3.767990656000 dcy

stealth address amount amount idx
00: 43ee288e97e6ec2b6e3abb25175746f3f0d54f6e55c16b8a7455b7421399ff71 3.767990656000 1108769 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": 667566, "vin": [ { "gen": { "height": 667556 } } ], "vout": [ { "amount": 3767990656, "target": { "key": "43ee288e97e6ec2b6e3abb25175746f3f0d54f6e55c16b8a7455b7421399ff71" } } ], "extra": [ 1, 164, 95, 219, 169, 248, 157, 11, 204, 213, 231, 98, 116, 232, 149, 160, 132, 48, 27, 241, 5, 239, 116, 123, 43, 42, 45, 183, 25, 223, 233, 197, 90, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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