Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d498ae315ad60c245876bfec782db54e1bec05831c449e18c7e8481fd978a23f

Tx prefix hash: eb73eb1bb1d15dbd8cdb4a7f4161f0f91e8bae739697a1a26539224d686a8dc5
Tx public key: fa27ee5be787181ca6033a033d35dd82bae962f789a0d4d8f455abbb55183cbd
Timestamp: 1581203190 Timestamp [UCT]: 2020-02-08 23:06:30 Age [y:d:h:m:s]: 04:321:15:44:23
Block: 60941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122000 RingCT/type: yes/0
Extra: 01fa27ee5be787181ca6033a033d35dd82bae962f789a0d4d8f455abbb55183cbd021100000028d81c26c0000000000000000000

1 output(s) for total of 385.547584123000 dcy

stealth address amount amount idx
00: a62dd16a95327a0c4f8ae319b83c3d2de52bb2286ea481f261a6d9748f39b0f2 385.547584123000 112338 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": 60951, "vin": [ { "gen": { "height": 60941 } } ], "vout": [ { "amount": 385547584123, "target": { "key": "a62dd16a95327a0c4f8ae319b83c3d2de52bb2286ea481f261a6d9748f39b0f2" } } ], "extra": [ 1, 250, 39, 238, 91, 231, 135, 24, 28, 166, 3, 58, 3, 61, 53, 221, 130, 186, 233, 98, 247, 137, 160, 212, 216, 244, 85, 171, 187, 85, 24, 60, 189, 2, 17, 0, 0, 0, 40, 216, 28, 38, 192, 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