Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af5653817d71b6b520709cf06380321c241aa82ea75bd6597a3b598078b12c84

Tx prefix hash: 63af1db8318dbeecdef1a4ebd2cd2740424f4b03e086e8e3ae4a5840f295318a
Tx public key: ea2e462738c583d2ee4848a614f0331a8fcbd3007518e5506f4943b02507938d
Timestamp: 1699245917 Timestamp [UCT]: 2023-11-06 04:45:17 Age [y:d:h:m:s]: 02:088:07:20:40
Block: 885496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582814 RingCT/type: yes/0
Extra: 01ea2e462738c583d2ee4848a614f0331a8fcbd3007518e5506f4943b02507938d0211000000074b8f5122000000000000000000

1 output(s) for total of 0.714470283000 dcy

stealth address amount amount idx
00: b6bbd09e0d1d3da11ef2fe26ca6967d2d93a460395e9fc9bf06f66cac1d922cc 0.714470283000 1341271 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": 885506, "vin": [ { "gen": { "height": 885496 } } ], "vout": [ { "amount": 714470283, "target": { "key": "b6bbd09e0d1d3da11ef2fe26ca6967d2d93a460395e9fc9bf06f66cac1d922cc" } } ], "extra": [ 1, 234, 46, 70, 39, 56, 197, 131, 210, 238, 72, 72, 166, 20, 240, 51, 26, 143, 203, 211, 0, 117, 24, 229, 80, 111, 73, 67, 176, 37, 7, 147, 141, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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