Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 672eec398f60885310d7992b58be5a8417c4b588cd293e870e90faf02fae3a4e

Tx prefix hash: 63845d3197333d9475ce6a2da9722d6b3fc46b249eed4c2e4b907923131c53c8
Tx public key: 1b3f0299670e0eb6ade560173eebe31be924b779311e4af1a3b0b85b05af847d
Timestamp: 1704482229 Timestamp [UCT]: 2024-01-05 19:17:09 Age [y:d:h:m:s]: 01:099:05:35:25
Block: 928892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332058 RingCT/type: yes/0
Extra: 011b3f0299670e0eb6ade560173eebe31be924b779311e4af1a3b0b85b05af847d0211000000020011055b000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 24ca59060b15e056798f8f2ac3a8afe5272f2d66add9f51a9cd442dd4e87a42d 0.600060000000 1386756 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": 928902, "vin": [ { "gen": { "height": 928892 } } ], "vout": [ { "amount": 600060000, "target": { "key": "24ca59060b15e056798f8f2ac3a8afe5272f2d66add9f51a9cd442dd4e87a42d" } } ], "extra": [ 1, 27, 63, 2, 153, 103, 14, 14, 182, 173, 229, 96, 23, 62, 235, 227, 27, 233, 36, 183, 121, 49, 30, 74, 241, 163, 176, 184, 91, 5, 175, 132, 125, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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