Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93940d7935fafd19a942b3701510134ea435faf313efd1f55fa96e9fc713c1fb

Tx prefix hash: db59b77832c0b8c1b82bd9dc33e2de57db725f7ed79d4c1927fad23f1d8490ff
Tx public key: 986983acafe38e042edaceb8edee37bbec557983298e8a8c238c55f1f404f827
Timestamp: 1722210243 Timestamp [UCT]: 2024-07-28 23:44:03 Age [y:d:h:m:s]: 00:257:03:04:03
Block: 1075875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183685 RingCT/type: yes/0
Extra: 01986983acafe38e042edaceb8edee37bbec557983298e8a8c238c55f1f404f82702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2cb4f90893fb20f1430195da864b8b052198e2829c9cc8c09d7a66a2e15c924 0.600000000000 1548406 of 15

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": 1075885, "vin": [ { "gen": { "height": 1075875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2cb4f90893fb20f1430195da864b8b052198e2829c9cc8c09d7a66a2e15c924" } } ], "extra": [ 1, 152, 105, 131, 172, 175, 227, 142, 4, 46, 218, 206, 184, 237, 238, 55, 187, 236, 85, 121, 131, 41, 142, 138, 140, 35, 140, 85, 241, 244, 4, 248, 39, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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