Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d528465c52fe0281a80ca56aab8720e8fcad75b705db3fb500422cdb285a735a

Tx prefix hash: 6d215455a57fb47bd1f5174e4198ee3195b71e1baef8adc30a4acf2960c68179
Tx public key: 173b31e5352a4a9fc0c33cba60c0b29b1917f852a992f274f9e575e8c7464fea
Timestamp: 1661474801 Timestamp [UCT]: 2022-08-26 00:46:41 Age [y:d:h:m:s]: 02:205:18:26:51
Block: 573871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 668314 RingCT/type: yes/0
Extra: 01173b31e5352a4a9fc0c33cba60c0b29b1917f852a992f274f9e575e8c7464fea021100000003e6d27f9c000000000000000000

1 output(s) for total of 7.700647593000 dcy

stealth address amount amount idx
00: 9acdc9bcb4e0e7d6aacf21e27b63402cab3e54e1ab22e017aacb6daff9bf9553 7.700647593000 1007169 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": 573881, "vin": [ { "gen": { "height": 573871 } } ], "vout": [ { "amount": 7700647593, "target": { "key": "9acdc9bcb4e0e7d6aacf21e27b63402cab3e54e1ab22e017aacb6daff9bf9553" } } ], "extra": [ 1, 23, 59, 49, 229, 53, 42, 74, 159, 192, 195, 60, 186, 96, 192, 178, 155, 25, 23, 248, 82, 169, 146, 242, 116, 249, 229, 117, 232, 199, 70, 79, 234, 2, 17, 0, 0, 0, 3, 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