Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58131391fc01b783bde938a541fb5419b26ae1ab089f1608bf1e5ebc5f884b7c

Tx prefix hash: 85f1b046250fa8f157e858a12e66c189f4c616dc3b6b8514e58cb7fa7675a951
Tx public key: 2679922c00d221bdbf4b7d35bb552cad45094cc243eab4b5cbed8decb2ebb344
Timestamp: 1673869390 Timestamp [UCT]: 2023-01-16 11:43:10 Age [y:d:h:m:s]: 02:116:07:31:09
Block: 675970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604821 RingCT/type: yes/0
Extra: 012679922c00d221bdbf4b7d35bb552cad45094cc243eab4b5cbed8decb2ebb3440211000000018b7b6602000000000000000000

1 output(s) for total of 3.533708572000 dcy

stealth address amount amount idx
00: 63f70a7f7c3b9524c455ce3e31bddfd40e1e625b7cbd9d409f4d3f248e50de66 3.533708572000 1117663 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": 675980, "vin": [ { "gen": { "height": 675970 } } ], "vout": [ { "amount": 3533708572, "target": { "key": "63f70a7f7c3b9524c455ce3e31bddfd40e1e625b7cbd9d409f4d3f248e50de66" } } ], "extra": [ 1, 38, 121, 146, 44, 0, 210, 33, 189, 191, 75, 125, 53, 187, 85, 44, 173, 69, 9, 76, 194, 67, 234, 180, 181, 203, 237, 141, 236, 178, 235, 179, 68, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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