Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9476a7170a182e8091bde30fabbe9653ced0f0670f99aefcdf17c72fecadb41

Tx prefix hash: 254b4307f8a3f31be90c046837ef5cca92cc9eca5f0e0dc6a88640751a962d71
Tx public key: a38ce83a4b72b7af83ab86a05b32ae0303c850329de40ca96d94b089a4947d05
Timestamp: 1644147586 Timestamp [UCT]: 2022-02-06 11:39:46 Age [y:d:h:m:s]: 03:037:03:33:07
Block: 433230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805971 RingCT/type: yes/0
Extra: 01a38ce83a4b72b7af83ab86a05b32ae0303c850329de40ca96d94b089a4947d0502110000000137cb3088000000000000000000

1 output(s) for total of 22.517982175000 dcy

stealth address amount amount idx
00: be8a1754c9f138e1cff6983e473d0c0f98b09c97b6d25199176e0cc6a3c678aa 22.517982175000 843873 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": 433240, "vin": [ { "gen": { "height": 433230 } } ], "vout": [ { "amount": 22517982175, "target": { "key": "be8a1754c9f138e1cff6983e473d0c0f98b09c97b6d25199176e0cc6a3c678aa" } } ], "extra": [ 1, 163, 140, 232, 58, 75, 114, 183, 175, 131, 171, 134, 160, 91, 50, 174, 3, 3, 200, 80, 50, 157, 228, 12, 169, 109, 148, 176, 137, 164, 148, 125, 5, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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