Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79716a03dfcd88fa1b46fb0642988bcc606ae91b37cff0fcfa39d8bda6fa5000

Tx prefix hash: 34202c8804ebf0f8d23aacb27401a7936afbd8f5f2850f2905299e92c056fa71
Tx public key: dd9967c21f299c225c8f2bbedd9abbbf5ad573ed64b1f71e91da30d1c545d806
Timestamp: 1582999910 Timestamp [UCT]: 2020-02-29 18:11:50 Age [y:d:h:m:s]: 05:072:07:07:25
Block: 74295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205960 RingCT/type: yes/0
Extra: 01dd9967c21f299c225c8f2bbedd9abbbf5ad573ed64b1f71e91da30d1c545d8060211000000094943cd9f000000000000000000

1 output(s) for total of 348.201487430000 dcy

stealth address amount amount idx
00: ee13a9fa7d0203a20b295252394402d10701e2e97d5438efb85a59ad10001d0d 348.201487430000 137402 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": 74305, "vin": [ { "gen": { "height": 74295 } } ], "vout": [ { "amount": 348201487430, "target": { "key": "ee13a9fa7d0203a20b295252394402d10701e2e97d5438efb85a59ad10001d0d" } } ], "extra": [ 1, 221, 153, 103, 194, 31, 41, 156, 34, 92, 143, 43, 190, 221, 154, 187, 191, 90, 213, 115, 237, 100, 177, 247, 30, 145, 218, 48, 209, 197, 69, 216, 6, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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