Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ecec99445e0e6973cccbc3e0f8b5f70e31eab2dc1e457f75ac7440b98e4363

Tx prefix hash: 06ed4a6a3dbd05b270e644ad0d62e8560669ae8d3d202757f1082d16e0f1829e
Tx public key: 243c59c5da9ea8e32edc60806e5462b951412edca15dc2adbf58003f87c89846
Timestamp: 1634647537 Timestamp [UCT]: 2021-10-19 12:45:37 Age [y:d:h:m:s]: 03:355:20:34:25
Block: 356175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1029892 RingCT/type: yes/0
Extra: 01243c59c5da9ea8e32edc60806e5462b951412edca15dc2adbf58003f87c898460211000000163fc41461000000000000000000

1 output(s) for total of 40.536363364000 dcy

stealth address amount amount idx
00: f78eb304ea7361173bf1eead503d461a6a5fa7dc4b593ecf28b127aec5958e42 40.536363364000 726823 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": 356185, "vin": [ { "gen": { "height": 356175 } } ], "vout": [ { "amount": 40536363364, "target": { "key": "f78eb304ea7361173bf1eead503d461a6a5fa7dc4b593ecf28b127aec5958e42" } } ], "extra": [ 1, 36, 60, 89, 197, 218, 158, 168, 227, 46, 220, 96, 128, 110, 84, 98, 185, 81, 65, 46, 220, 161, 93, 194, 173, 191, 88, 0, 63, 135, 200, 152, 70, 2, 17, 0, 0, 0, 22, 63, 196, 20, 97, 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