Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296754d4ad67cfd3ed2afe6f6c0ecca9719a795fbddf636ee7546b8e291a2c7e

Tx prefix hash: 027386149d60d8c7b16c08c3de52ce18f1ada21b910c98100f32c445d4e7f9d1
Tx public key: 8c656470a1f229a927dc6e4db007e0d4a7f5ceaeff39c3956b32d28dbc74b2f5
Timestamp: 1670425569 Timestamp [UCT]: 2022-12-07 15:06:09 Age [y:d:h:m:s]: 02:042:07:41:31
Block: 647448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552170 RingCT/type: yes/0
Extra: 018c656470a1f229a927dc6e4db007e0d4a7f5ceaeff39c3956b32d28dbc74b2f50211000000027e406890000000000000000000

1 output(s) for total of 4.392745048000 dcy

stealth address amount amount idx
00: 69fa93adec55f1d6e45bc543c1dca6ef2ccb4c799e4a5bb34115a781210e4f5c 4.392745048000 1087723 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": 647458, "vin": [ { "gen": { "height": 647448 } } ], "vout": [ { "amount": 4392745048, "target": { "key": "69fa93adec55f1d6e45bc543c1dca6ef2ccb4c799e4a5bb34115a781210e4f5c" } } ], "extra": [ 1, 140, 101, 100, 112, 161, 242, 41, 169, 39, 220, 110, 77, 176, 7, 224, 212, 167, 245, 206, 174, 255, 57, 195, 149, 107, 50, 210, 141, 188, 116, 178, 245, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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